Skip to main content
Version: 11.0

Simulated Discovery

You might want to test the discoverability of a single device before running the actual device discovery. This could save you the trouble of re-running the full discovery if you find that a segment of your network is not accessible from Resolve Insights. Use simulated discovery to check the connection to a single machine.

note

Only Windows compute devices are supported for simulated discovery.

Simulated discovery tests the two-way communication between Insights and the target device—whether Insights can log in to the device and whether it can pull data from it.

Take these steps to start simulated discovery:

  1. Log in to any of your DC nodes.
  2. Run the following command:
    netra_windows -u <username> -d <domain> -a <ip-address> -c "<command>"
    Where:
    • <username> is the Windows user account to use to log in to the device.
    • <domain> is the domain of the Windows user. Optional. If omitted, the tool will try to log in as a local user.
    • <ip-address> is the IP address or hostname of the Windows machine that you want to discover.
    • "<command>" is the command that you want to execute on the Windows machine after it is discovered and if the authentication is successful. If omitted, the command that is executed is: wmic service where (state='Running') get processId, DisplayName.
  3. Enter your password when prompted.

Unless you specify a different command to execute, the DC tries to discover the machine over different protocols. This could take a while. Any errors pointing out closed ports or protocols not allowed are normal.

At the end of the process, if successful, you see a printout of all services found to be running on the device together with a port number.